Repository navigation
DEV-1395: Release workflow for ShimmerCapture - #146
Merged
Merged
Conversation
Automates the Confluence procedure "ShimmerCapture Android Release (shimmerServiceExample)": builds the shimmerServiceExample release APK, signed with the upload keystore from repository secrets the same way Android Studio's Generate Signed APK does, tags ShimmerCapture_v<versionName> and creates the GitHub pre-release with the APK. With google_play ticked it also uploads the APK to Play's Production track as a draft, to be sent for review in Play Console. The version stays committed in build.gradle: the workflow refuses a version already tagged, a versionCode no higher than the last release's, and a build not set to APP_RELEASE_TYPE.PUBLIC. PRs that change the workflow dry-run it unsigned. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
RELEASING.md walks through a release: the uprev PR, an optional signed dry run, the workflow run, sending the draft for review in Play Console, failures and their fixes, and the secrets. Linked from the module README, the workflow header and AGENTS.md. Co-Authored-By: Claude Opus 5.5 <[email protected]>
JongChern
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automates the Confluence procedure ShimmerCapture Android Release (shimmerServiceExample) as a dispatch-only workflow, Release ShimmerCapture (
.github/workflows/release-shimmercapture.yml).How to release:
shimmerServiceExample/RELEASING.mdhas every step, from the uprev PR to sending the draft for review in Play Console, plus failures and their fixes and the secrets. It is linked from the module README, the workflow header andAGENTS.md.What a run does
ShimmerCapture_v<versionName>is already tagged, ifversionCodeis not higher than the previous ShimmerCapture release's (Play rejects a code it has seen), or ifMainActivity.appReleaseTypeis notPUBLIC.shimmerServiceExample, signing with theandroid.injected.signing.*properties that Android Studio's Generate Signed APK uses, sobuild.gradleneeds no signing config. Checks the APK's versionName/versionCode withaapt2and its signature withapksigner.ShimmerCapture_v<versionName>and creates a GitHub pre-release with the APK and generated notes since the previous ShimmerCapture tag (pre-release, like v1.3.3, so the Android API release stays Latest).google_playticked: uploads the same APK to Play's Production track as a draft. Someone still reviews it in Play Console and clicks Send changes for review.dry_runbuilds without publishing, from any branch. PRs that change the workflow dry-run it unsigned: the keystore is only used on manual runs, because a PR build runs the PR's own Gradle scripts.The version stays committed in
build.gradlerather than typed into the run (unlikerelease.yml), because Play needs a rising versionCode and the file is the only record of the last one. So each release still starts with an uprev PR raisingversionNameandversionCode; the workflow refuses to run if that was forgotten. This PR carries the uprev for the next release (1.3.4, versionCode 35) as its own commit.Repository secrets
All added 2 Nov 2026:
SHIMMERCAPTURE_KEYSTORE_BASE64: the upload keystore, base64-encodedSHIMMERCAPTURE_KEYSTORE_PASSWORD,SHIMMERCAPTURE_KEY_ALIAS,SHIMMERCAPTURE_KEY_PASSWORDGOOGLE_PLAY_SERVICE_ACCOUNT_JSON: JSON key of the service accountgithub-shimmercapture-release, in the Play account's Google Cloud project Google Play Android Developer. Invited in Play Console (Users and permissions) on 2 Nov 2026 with release rights on ShimmerCapture only; new permissions can take up to a day to apply.Signing with the real keystore is checked by a
dry_runon master after merge; it prints the certificate SHA-256 to compare with Play Console's upload certificate.Tested locally
:shimmerServiceExample:assembleReleasepasses, includinglintVitalRelease, so the DEV-379 lint error no longer occurs.shimmerServiceExample-release.apk, and theaapt2/apksignerchecks read it correctly.PUBLIC).🤖 Generated with Claude Code